5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
- Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 3-16: Using GUI Features of the Image Editor

The WIDGET File/Record


The WIDGET file contains records for storing each GUI element in your design.  A WIDGET record will contain the fields found on the GUI Attribute screens for each of those elements.  When you are adding fields, buttons, labels, etc, and modifying the GUI Attribute in your process, Appx is maintaining the WIDGET file for you.  The WIDGET file can also be read and modified at run time by coding statements in your process.  The ability to modify the WIDGET record at run time provides the ability to customize the look of the application based on variable conditions. 

Nearly every element of an image can have GUI attributes.  The Widget file therefore will have many records for each image.  Access to individual records within the WIDGET file is accomplished by setting the --- WIDGET NAME alternate key field and then READ'ing the WIDGET file.  The file must be read with HOLD=1 in order to save the changes with a REWRITE statement.  The WIDGET NAME field is entered on the GUI attribute screen.  The WIDGET NAME is not unique.  You can design your process to have the same name for a set of widgets.  For example;  all Label elements could have a name of STANDARD LABEL.  

You can then set up a read loop in the Pre-Display Event Point to read all the WIDGET NAME record that match STANDARD LABEL and set individual GUI attributes as illustrated in the following example. 

The above example would read all the WIDGET records by the alternate key WIDGET NAME containing the value STANDARD LABEL.   When a record is found the Text Color (forground color) is set  to blue (255), the font is set to Arial, and the font scale is set to 80%.  Changing the color requires setting the RGB hex values and the NL flag to 1.  The NL flag tells Appx to change the color.  Refer to Making Color Selections, to determine color hex values. 

To determine the --- WIDGET field name while in the ILF editor you can scan the --- WIDGET to see all the fields available.  Note that all possible WIDGET fields are listed when scanning the file and not all will pertain to your currently selected widget.

If you add (create) a Widget Record at run time using ILF, in addition to your GUI attributes you must also complete the fields in the primary key for the Widget Record. Following is a list of the Primary Key for the Widget Record (WIDGET KEY). 

 

Application Design Manual                                         "Powered by Appx Software"

1345

©2006 By APPX Software, Inc. All Rights Reserved